fix(ci): switch release-please to manifest mode for multi-package releases#6
Merged
matmilbury merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
…eases The skill sub-package (packages/skill) was not managed by release-please, so its version was never bumped. This caused npm publish to fail with 'You cannot publish over the previously published versions: 0.1.3'. Switch from simple release-type mode to manifest mode with: - release-please-config.json defining both . and packages/skill - .release-please-manifest.json tracking current versions - linked-versions plugin to keep both packages in sync - workflow updated to use releases_created (manifest output) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
publishjob in CI was failing because the skill sub-package (packages/skill) version was never bumped by release-please. It was stuck at0.1.3(already published), causing:Release-please was configured in simple
release-type: nodemode, which only manages the rootpackage.json. The sub-package atpackages/skill/package.jsonwas invisible to it.Fix: Switch to manifest mode with two config files so release-please manages both packages. A
linked-versionsplugin keeps them in sync so they always share the same version number.Type
Changes
release-please-config.json(new): Defines both.andpackages/skillas managed packages withlinked-versionsplugin.release-please-manifest.json(new): Tracks current published versions (0.2.1root,0.1.3skill).github/workflows/release.yml: Removedrelease-type: node(now in config), switched output fromrelease_createdtoreleases_created(manifest mode)Checklist
QA Instructions
mainpackage.jsonfiles and generating CHANGELOGs for both packages@eterna-hybrid-exchange/openclaw-pluginand@eterna-hybrid-exchange/eterna-trading-skillto npmRelated